Fix OpenSearch client compression setting#26633
Open
moesterheld wants to merge 6 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The setting
elasticsearch_compression_enabledwas used in the client (in both opensearch2 and opensearch3 storage modules) to toggle thechunkedsetting of the client.This PR fixes this to correctly toggle the
compressionsetting.Additionally, the
opensearch-javaclient was bumped to 3.9.0 and the parameter documentation clarified to state that this affects both requests and responses.Motivation and Context
fixes wrong handling of compression settings
How Has This Been Tested?
manually by setting compression to enabled
Screenshots (if appropriate):
Types of changes
Checklist: